Developer CD Series 1999 February: Tool Chest/Dev.CD Feb 99 TC.toast/Tool Chest/Development Kits/MPW etc/Documentation/Debuggers/SADE/SADE 1.3.3 Release Notes/SADE 1.3.3 Release Notes

Text File | 1997-03-24 | 81.2 KB | 908 lines | [ONLN/HLX2]

SADE 1.3.3
Release Notes
Copyright Apple Computer Inc.
1993. All rights reserved.
Changes Since SADE 1.3.2
n    SADE would occasionally fail while defining a certain number of user strings on systems with greater than 16MB of RAM.  This has now been fixed.
n    Under certain low memory conditions, SADE may not have been able to retrieve correct type information.  This has now been fixed.
Changes Since SADE 1.3.1
n    SADE was handling trace exceptions generated by MacsBug.  While running SADE in the background, if you attempted to set an address break from MacsBug and then exe-cute “go,” SADE would take control.  This has now been fixed.
Changes Since SADE 1.3
n    BreakIf was failing under some situations. This has now been fixed.
n    SADE was writing to NIL under low-memory conditions.  This has now been fixed.
n    Increased “preferred” memory partition size to 1.5 megabytes to be able to handle MacApp without running out of memory.
n    Stepping after hitting a one-instruction source statement would stop two source instructions later instead of at the next instruction.
n    SADE now displays the correct CCR value in the registers window.
n    You can now set the values of the SR/CCR register.
n    SADE no longer uses the MPW Shell’s small icon for the Notification Manager.
n    SADE now works properly under VM on 040 machines.
n    The Extras menu item Show Self has been separated into two items:
    Show **this (Command-4), and
    Show *this.
    Show **this functions exactly as Show Self did in SADE 1.3 Final. However, for C++ programmers who are not using MacApp, the Show *this menu item is more useful. Therefore, we have included both.
Changes Since SADE 1.3B2
n    CFront  generates incorrect symbols for any PascalObject with a forward declaration. In the member functions, CFront  says that this is a *TType, then casts all references through this to (**(TType**)this). To alleviate this problem some hacks were put in SADE.  If your program contains the resource %__MethTable (as is the case with MacApp programs), and if you have a type which the symbol file specifies to be a pointer to a PascalObject (a record whose first element is a __vtable), SADE will make itself believe that the type really is a pointer to a pointer to that object. As a con-sequence of this fix, if you singly dereference a handle to a PascalObject, the pointer value displayed will be correct, but the type displayed will be a handle.

The newly provided menu item  Twice Dereference Selection (Command-5), explained below, makes displaying objects through handles much easier.
n    A new menu called Extras was added. Four of the menu items under this menu make displaying objects easier, and the last one makes changing the value of objects easier.
    • Show Value In Context (Command-2) and
    • Show Dereferenced Value In Context (Command-3)
     The old style Show Value menu items have no context, they simply follow scoping rules. Thus, if you select fNext, it will try to show you an automatic fNext, a global fNext, this^.fNext or this^^.fNext.
    These new menu items put the value of the selected variable in a separate window.  For subsequent selections, the name of the window provides the context.  E.g. if you select fNext in your source file and do a Command-2, you will most likely get this^^.fNext.  However, if you had previously displayed a variable newWindow, and select fNext in that window, Command-2 will show you newWindow.fNext.

Since these windows are really files, when the length of the name of the thing to be displayed exceeds 32 characters, it will be displayed in the Value window instead. These menus do not work if your selection has a colon (:) in it. These commands are slightly slower than the regu-lar show value menu items, but having a separate window for each variable far outweighs the slight speed penalty.

• Set Value (Command-=)
Changing variables has always been difficult in SADE . The problem is that SADE shows you structured values, but you probably need to change only a field in a struc-tured object. It would be nice to type over a displayed value in a window to the value you want.  Unfortunately, it is not that simple.
    If you are trying to change a simple variable, simply highlight its name and select the menu item Set Value.  From the displayed dialog box, you can verify that SADE is going to change the variable you wanted. If the proper object is selected, type in the value you want.  You can type in expressions instead of simple numbers.  You can also type in the name of a complex object whose type matches that of the left hand side.

In implementing this operation, SADE first evaluates the left hand side, then evaluates the expression you typed in, and may display error messages if it finds any problems.  After that SADE will try the actual assignment; that too may fail because of incompati-ble types for the left and right hand sides.

To change a field buried in a structure, you have to peel the outer levels. E.g. if you want to change
    FirstLevel.SecondLevel->Member
do a Command-2 after selecting FirstLevel. This gives you a window named FirstLevel. In that window, select the word SecondLevel and do a Command-3. Now you have a window named FirstLevel.SecondLevel^. In this window select the text Member and select Set Value or Command-=.
    Two new menu commands were added to the Extras  menu to make debugging MacApp applications written in C++ easier.
    • The menu item Show Self (Command-4) displays **this in a separate window.
You must be stopped inside a MacApp method for this menu to work.

C++ programmers who are not using MacApp may wish to edit the SADE routine __ShowSelf__ in the file SadeStartup file so that this menu displays *this instead.
    • The menu item Twice Dereference Selection (Command-5) makes displaying objects through a handle to them a one step process. The value is displayed in a sepa-rate window, as in the previous commands.

This menu is implemented in the file SadeUserStartup•Extras.  You can remove this file without affecting SADE's behavior in any other way.
n    The order in which SADE startup files are executed is:
    • SadeStartup
    • SadeUserStartup
    • all files whose names starts with SadeUserStartup•. These files are executed in alpha-betical order.

If you want to override anything defined in the file SadeUserStartup•Extras, create a file named something like SadeUserStartup•zzz, so that it is alphabetically later.
n    SADE will place all temporary files in the sub-folder called SADE Scratch inside the SADE launch directory.  If the folder does not exist, SADE will create it.  During exit, SADE will delete all SADE created files from this directory.

One side effect of this behavior is that SADE will no longer remember the position of the temporary windows like Values. If you prefer the old behavior, override the scratch directory by adding the following line to your SadeUserStartup file:
    __ScratchDir__ := SADEDir
n    When SADE needs to open a source file, it tries much harder now.  The symbol file provides SADE with either a full path name or just the leaf name, depending on the way the file was compiled. In addition, the modification date of the source file when it was last compiled is also provided. Here is the list of actions SADE goes through to find a source file:
    • Check if any of the open files have the same leaf name and matching date. If not,
    • If the symbol table specified a full path name, try the full path to open the file. If not,
    • Try to find a file in the default directory with the same leaf name. If not,
    • Try to find a file in any of the directories in the SourcePath. If not,
    • Check if any of the open files have the same leaf name but a wrong date. If not,
    • Ask the user to navigate the directory structure to find a file with the same leaf name.
    Check the modification date of the file found in any of the above ways, if there is a mismatch, give the user a chance to find a better match. If the user finds a file in a new directory, add the new directory to the source path.
n    If you open a source file in a directory which is not in the current source path, and try to set a break point in it, if SADE finds the symbol for a file with that name, SADE will add the new directory to the source path.
n    When SADE displays a record, the name of the record is displayed in addition to its contents.  Occasionally SADE may display names like __O32, these are generated by CFront in situa-tions like anonymous unions or structs.
n    When the conditional break table is full, we shift the oldest break point out instead of deleting all old conditional breakpoints. You still get the warning.
Changes Since SADE 1.3B1
n    SADE will now set the Sourcepath variable for you.  If SADE cannot find the applica-tion’s source files in the same directory as the symbol file, it will prompt you to find the source file.  In addition, while debugging your code, if you step into a procedure defined in a separate source file and that file is in a different directory than those de-fined by the sourcepath vari-able, SADE will prompt you to search for that file as well. SADE will add the new directory indicated to the sourcepath.
    Note, however, that SADE does not clear the Sourcepath variable each time you kill your application. This way, you can continue targeting the same application without SADE prompting you each time to locate your source files.
n    SC7 is a new script available in the SADE folder.  When executed from the worksheet, you may use the procedure StackCrawl7 or sc7 defined in the script to show a pos-sible calling chain sequence.  StackCrawl7 is similar to the MacsBug command sc7.  It is useful for dis-playing the calling sequence when the built in A6 based stack command does not work.
n    MacsBug and ROM symbols will now be displayed in a disassembly. When there is no sym-bolic information available and your code has been compiled with MacsBug sym-bols, SADE will display MacsBug information, e.g.:
        BEQ.S      µINITIALIZE+$00BA   ; 00BE7B22
n    SADE will now display up to the first 20 elements of an array instead of just the first element.
n    When displaying the value of a pointer to a string, SADE will always display the pointer value, then the string if it meets the criteria described below.
n    C does not have a built-in string type. The following heuristic is employed to determine if a signed or unsigned character array contains a string:
    // Get past the printable characters
    for (i = 1; i < len; i++)
        if (!isgraph(string[i]) && !isspace(string[i]))
            break;

    // Is this a CStr?  Must terminate with a null.
    if (string[i] == 0)
        // The first byte must be printable
        if (isgraph(string[0]) || isspace(string[0]))
            goto display_CStr;

    // Is this a PStr?  The string[length] byte must be printable
    if (string[0] < i)
        goto display_PStr;
    The significance of this is that if you have partially constructed strings in a char array, SADE may decide you do not have a string. If string display fails, SADE will show you the first 20 elements of your array, which may give you a clue as to why the array did not display as a string.  One peculiar case is when the first element of your array contains a zero, in which case SADE will believe that it successfully displayed a null string, and will not show the rest of the array.  In most cases this is the right answer, but not always.
    Also note that you can type coerce your array to display it as a PString:
        ^PString(@YourArray)
    Similarly,  you can coerce your array to display it as a CString:
        ^CString(@YourArray)
    Note that Pascal strings are shown with single quotes, e.g. 'string', whereas C style null-terminated strings are shown as "string".
XCMDs, etc.
n    SADE’s default behavior does not allow you to set breakpoints in resources which are not of the type 'CODE'.  You can change this behavior by setting the built-in SADE variable BreakInNonCODERsrc to 1. Be warned, however, that as SADE must then check every re-source which is being loaded into memory, this option will slow things down.
n    You can debug HyperCard XCMDs and XFCNs with SADE. To be able to debug XCMDs, follow these steps.
(1)    Compile and link your XCMD (or XFCN ) with symbolics.
(2)    Using ResEdit, remove the XCMD resource out of the original stack and paste it into the HyperCard application itself.
(3)    In SADE, you must set the SADE variable BreakInNonCODERsrc to 1.
(4)    Set the directory to the location of the .SYM file and set the sourcepath to the loca-tion of your sources.
(5)    Next, target HyperCard using the SYM file, e.g.:
Target "HD:HyperCard:Hypercard" using "HD:Examples:HyperXExample.SYM"
    You will see an “Initial program break encountered at...” message output to the worksheet, which indicates HyperCard itself was suspended.  From here, you may open your source file, set a breakpoint and execute your program.
    Note: this is not a fully supported feature of SADE.  Therefore, the above steps may not work in all instances.
n    Some applications may load your XCMD-type code resources in a subheap. To be able to debug them, you need to set another built-in SADE variable, CurTargetZone, to the ad-dress of that subheap.
n    Debugging printer drivers is analogous to debugging XCMDs and XFCNs.  Build the driver and paste the code resource you wish to debug into any application.  Remember to place the driver in the extensions folder (System 7.0) and select the driver from the Chooser.  Set the directory and sourcepath as mentioned above.  Set the variable BreakInNonCODERsrc to 1.  Target the application using the .SYM file you just cre-ated.  You may now set a break in your source file and execute the SADE command Go.
Known bugs
n    If you target an MPW tool and then before executing the tool from the MPW work-sheet, you set a break on the tool and quit SADE, the Shell may crash with a bus error.
n    If you step over the last statement in an MPW tool written in Pascal, you may get an address error in the Shell.
n    The SADEKey may not work until the target application has made an event call (for instance, WaitNextEvent).
    Pressing the SADEKey multiple times in a row may cause a crash.
    Targeting a running application and then hitting the SADEKey may not work.
n    The Stack command does not support the documented option at address.
n    If the Stack command is part of a break action, the stack will not necessarily be dis-played when the breakpoint is encountered.  A Printf command following the stack command will flush internal buffers, forcing any pending output.
n    SADE shows Pascal variables containing sets as integers, instead of showing the set elements with their names.
n    If you kill the target using the menu command, the watch variables are removed and the conditional break table is cleared. However, if you use the SADE command Kill, or quit the target, these clean up actions are not done. If you target again, the old watch variables may not be relevant.
n    There is a size limit of 1,006 bytes on the value which can be assigned to a SADE vari-able.  As a consequence of this, you can not use the Show Value menu to display a variable of size greater than 1,006 bytes.  You can, however, enter the name of the variable you want to display in a writable window and hit enter to get its value.
n    Assigning a large C structure to a SADE variable in a define statement may display garbage as part of the error message.
n    To reference Pascal variables declared at UNIT scope, when the PC is not in the scope of the unit, use the syntax, \UNITNAME.variablename. To reference Pascal variables declared at PROGRAM scope use the syntax, \variableName; referencing them as \PROGRAMNAME.variableName does not work.
n    When running SADE on a Classic and targeting a MacApp program, once you step into a MacApp method, SADE can’t retrieve the symbol information for the source.
n    If Stop Before Constructor is set and after targeting you step over main() in a C or C++ application, quitting the application will produce an error message of "Data Initialization Failed!".
n    Stepping over a CHK or TRAPV instruction which will cause an exception results in a crash.
n    If you enter SADE by calling a SysError() call, the condition code registers displayed will be invalid.
n    Since SADE allows users to use symbol files which may not have been produced as part of the application build, SADE can not do any checking of the symbol file date relative to the application date. If you see the error message:
    Logical end-of-file reached during read operation (OS error -39)
when you target a process, it probably means that your application and the symbol file are out of sync.
n    The current symbolic information does not include information specific to classes. While SADE supports commands like Break Class TSomething, it requires SADE to scan the entire symbol file to find matching names.  As a result, this command can take a long time.
n    Similarly, the symbolic information does not include information about static class variables, and SADE does not display these when a class object is displayed. To see a class static vari-able, you have to fully qualify the name, e.g.
    TClass:fgStaticField
n    If you have trace points set within the main event loop of your target program, so that they are continually displayed in the worksheet, the target application's menu may oc-casionally overlap the SADE menu.  This is only a cosmetic problem in the Process Manager (System 7.0) and in Multifinder (System 6.0) and should not affect the func-tionality of your program.
n    Users of Object Pascal who are not using MacApp should always specify the linker's method table optimization option -opt on. Otherwise, stepping over method calls will not work.  This is because SADE changes the return address of the method’s caller, which confuses the method dispatch procedure (%_Method).  When %_Method fails, it intentionally executes a division by zero, which is what SADE reports.
n    SADE  cannot target background-only applications because of the way it works with the  Process Manager.  Workaround: Remove the background-only restriction from the applica-tion and debug.  Once your application is fully debugged, make it background-only again.
System 7.0 specific bugs
n    Under System 7.0, if you’ve targeted an application and stepped through your initial-ization code, even though your target is suspended, hiding SADE will cause the target to run.  This is a bug in the Process Manager.
n    If a file is open modifiable from a shared volume by one user, that file cannot be opened (read-only) for targeting by another user.
n    Do not launch two debuggers at the same time.  If you quit the second one launched, and try any operation in the first one, you will get the cryptic message:
#   Application made module calls in improper order  (OS error -603)
System 6.0 specific bugs
n    Special care needs to be taken when debugging MacApp programs under system 6.0.x.  After killing a program the first time, you may not be able to retarget the application and be forced to reboot.  This is because MacApp installs a VBL which is not being re-moved by MultiFinder after a kill.  This does not occur under system 7.0.  A work around is to always quit your application normally; do not kill the application from SADE.
n    SADE doesn’t handle script execution properly when the script is in the same folder as the target.  Workaround: fully qualify the path to the script before executing it.
n    There is a bug in Multifinder 6.1b9 which prevents you from being able to scroll the Apple Menu when the option key is held down.
n    If you use the target command when you already have a suspended target, the old target will not be restarted.
n    If you launch a target from SADE, and quit SADE without first killing it, when the tar-get quits, Multifinder will try to send a message to a non-existent process and cause a system crash.
n    The SADEKey cannot be changed under System 6.0.
n    SADE does not work with Maxima™ or Virtual (both from Connectix Corp.).
Compiler and Linker symbol generation bugs:
n    The compilers do not generate type information unless considered necessary.  If you have a type declared but do not have any object of that type, possibly used only for casting, no sym-bolics are generated for the type. Workaround: none. This is a compiler feature to minimize the symbol table size.
n    CFront typically generates constructor and destructor code at the beginning and end of syn-tactic blocks, gives them separate symbolic information records, but maps them to the same location in the source file. One observed behavior is stepping multiple times on the same source statement. Also, in this situation if you do a Break followed by an Unbreak, the loca-tion you set the breakpoint and the location you did the unbreak may not be the same, even if the selection looks identical. Workaround: none.
n    If the source code contains a series of declarations with assignments, CFront  produces incor-rect symbol information for these.  The observed behavior is that you need to single step as many times as there are declarations, but SADE keeps highlighting the first statement in the series.  After sufficient number of steps, SADE will jump over all the declaration code at once. Workaround: none.
n    C++ allows variables to be declared anywhere within a block.  When a program is stopped in a block before a variable comes into scope, SADE will display an incorrect value for the vari-able. A better behavior might be to say that the variable is not in scope.
n    CFront  passes a temporary file C.pipe.code to the C compiler. The C compiler incor-rectly assigns all global static variables to the unit C. For this reason, references to static variables in a file other than the current one does not work as expected. Workaround: instead of \FileName.StaticName, try \C.StaticName.
n    SADE can not print the values of anonymous unions in C++ correctly.  If you have:
struct Outer {
    int field;
     union {  // anonymous
        int cant_find;
        char another_cant_find;
    };
} Outer_thing;
    SADE is unable to display the value of Outer_thing.cant_find.  Workaround: If you look at the struct that CFront makes, you will see a name like __O1 for the anony-mous union.  If you say Outer_thing.__O1.cant_find then SADE will print it.
n    The  MPW 3.2 C compiler produces incorrect source statement information for state-ments with zero effect. The symptom is SADE's inability to set breakpoints in some routines. These show up most commonly in the process of compiling the output of CFront. Workaround: give -opt off flag to the compiler.
n    Both the MPW 3.2 C and Pascal compilers may assign multiple user variables to the same register. As a consequence, if you try to display a register variable whose value is currently dead, the value displayed may be wrong. Workaround: none.
n    If an enclosed Pascal procedure does not use any variable from the calling procedure, the MPW 3.2 Pascal compiler optimizes away the static link, but does not reflect this in the symbol information, resulting in incorrect display of arguments in the called func-tion. Workaround: use -opt on, nostatic or the -opt off flags to the Pascal compiler.
n    The MPW 3.2 Pascal compiler optimizes away the LINK instruction for functions which do not need stack storage for local variables, resulting in incorrect display of the stack. Workaround: give -opt off flag to the Pascal compiler.
n    The MPW 3.2 Pascal compiler generates incorrect symbol information about the loca-tion of local variables that are assigned to a FPU register . Workaround: none.
n    The MPW 3.2 Pascal compiler generates incorrect symbol information for enclosed functions with a procedure parameter. Workaround: none.
n    If your program contains single-statement for loops which should execute multiple times, SADE will appear to step through the loop only once.  This is due to the way that both the MPW 3.2 C and Pascal compilers generate symbol information. Workaround: set a break-point on the statement in the for loop and execute the Go command multiple times.
n    The MPW C and Pascal compilers occasionally generate incorrect symbol information for statement boundaries. Workaround: give -opt off flag to the compiler.
n    The current symbolic structure is somewhat limited in the size of the program that can be compiled with symbolics. The following table lists the number of different symbolic items a symbol file can contain.
Indexes to source statements (CSNTE)    4 G lines
Number of different source files    2K
Number of Functions (MTE)    64K
Number of blocks (CMTE)    64K
Number of Variables and Constants (CVTE)    64K
Number of Types (TINFO)    64K
Number of Labels (CLTE)    64K
n    Even if you stay within the above limits, the MPW 3.2 linker occasionally produces incorrect type information in large symbol tables. The Show Value menu item(s) nor-mally traps all internal errors and displays the message Undefined/Out of scope. However, if you type the name of the object in the worksheet and hit enter, SADE may then print the error message:
Symbol table error: Variable type table index could not be found.

Workaround:  The post 3.2 version of the linker shipped on the E.T.O. #5 disk fixes most of these problems. If you still find this problem, and if your program uses a rich hierarchy of classes, there is no workaround.  Even with a partially broken symbol file, you may be able to do most of the things you need to do. If your program is just big, if the size of your symbol table exceeds 1 megabyte, consider compiling parts of your application without symbols, and compile only the suspect parts with symbols.

You can use the SADE diagnostic command List Symbol to see the local variables and types that are defined in the current scope. This command will also show if any symbolic informa-tion associated with these objects is inconsistent.
n    Types which have global scope sometimes get  bound to a local scope, you can see the type definition only if the type is used in the current scope, or a containing scope. Workaround: none.
SADE 1.3 Manual Errata
n    The manual’s index was not generated correctly, so you may notice that each entry (after page 42) is off by two pages. Simply subtract the entry by 2 to get the correct page number.
n    The dialog box displayed when the target menu is selected is shown as a generic SFGetFile dialog box. In the released product  the dialog box contains the line
    Please select an application or symbol file.
n    In the section describing the different ways to target a program,  the manual states that you can drag and drop the icon of the target application on top of the SADE icon. For this feature to work, you may need to rebuild your desktop once.
n    The Target menu command as described in the manual is incomplete.  It states that you must select an application to debug, when in fact you may choose either an application or its .SYM file from the dialog box.  Then, if both files are not in the same directory, SADE will prompt you to locate the missing file. For instance, if you select a symbol file, e.g. AppName.SYM.,  and the application file is not in the same directory, SADE will put up a dialog asking you to locate the file AppName.  (Your application and .SYM file names do not have to be the same, however.)
n    The manual states that if your target program is suspended and you quit SADE, SADE will terminate the program. SADE will now restart your target application if it can.
n    The description of the Show Stack menu command is incomplete.  The command now displays a warning if the program counter points to a LINK instruction.
n    The Disasm command correlates source statement numbers with assembly code instructions. Branch instructions which use the new branch island option, are shown with a ^ character to denote the indirection.
n    The intentional bug introduced in the third C tutorial program, Sample2, can be more destructive than we intended. Running this program can cause your machine to hang.

If it does not hang your system, and you display the stack when the bus error occurs, the output is more informative than documented, in that SADE displays some MacsBug symbols.
n    SADE acquired the ability to prompt for source files when needed after the manual was finalized.  As a consequence you may never have to use the SourcePath command.  This behavior is not documented in the SADE manual, but is described in some detail at the beginning of these release notes.
n    SADE now includes an optional menu called Extras which is not documented in the manual, but is described earlier in these release notes.
    Contrary to what the SADE 1.3 Manual states, you can debug Hypercard XCMDs and XFCNs with SADE. The procedure for doing this is described earlier in these release notes.
`◊#ˇˇˇˇˇ#◊

_,Times

.°dONLNd)<=ù+ZW
SADE 1.3.3°dONLNd?êS
+T
Release Notes

°dONLNdè<õΩ(∑ZCopyright Apple Computer Inc.°dONLNd7ö<¶¢*1993. All rights reserved.

°dONLNdRfl<ÔÚ*HChanges Since SADE 1.3.2
 ÙXÙ,

Zapf Dingbats

°dONLNdk
<

A*!
n
°dONLNdm
J

Δ)OSADE would occasionally fail while defining a certain number of user strings on°dONLNdΩ
J

è*@systems with greater than 16MB of RAM.  This has now been fixed.

°dONLNd˛
+<
1A(
OZ
n
°dONLNd

'J
3
≈)LUnder certain low memory conditions, SADE may not have been able to retrieve°dONLNd
M
5J
A
=*3correct type information.  This has now been fixed.

°dONLNd
Å
{<
ãÚ(
¶ZChanges Since SADE 1.3.1 
êX
ê

°dONLNd
ö
£<
©A*!
n
°dONLNd
ú
üJ
´
‚)OSADE was handling trace exceptions generated by MacsBug.  While running SADE in°dONLNd
Ï
≠J
π
‹*Rthe background, if you attempted to set an address break from MacsBug and then exe°dONLNd>
≠
‹
π
‡(
’
˙
-°dONLNd?
ªJ
«
x(
„h=cute “go,” SADE would take control.  This has now been fixed.

°dONLNd}<'Á(BZChanges Since SADE 1.3 ,X,

°dONLNdî?<EA*!
n,
Courier

°dONLNdñ;JGz)BreakIf 
°dONLNdû;zG
ó)0;was failing under some situations. This has now been fixed.

°dONLNd⁄U<[A(yZ
n
°dONLNd‹QJ]
⁄)NSADE was writing to NIL under low-memory conditions.  This has now been fixed.

°dONLNd+k<qA(èZ
n
°dONLNd-gJs
 )QIncreased “preferred” memory partition size to 1.5 megabytes to be able to handle°dONLNduJÅ
*%MacApp without running out of memory.

°dONLNd•è<ïA(≥Z
n
°dONLNdßãJó
ø)OStepping after hitting a one-instruction source statement would stop two source(·Z
SADE 1.3.3)“
1)aE.T.O. #14 Release Notesˇ4◊#ˇˇˇˇˇ#◊

_,Times
.°dONLNd)J5
5+hQ6instructions later instead of at the next instruction.,

Zapf Dingbats

°dONLNd7C<IA(gZ
n
°dONLNd9?JK
ã)@SADE now displays the correct CCR value in the registers window.

°dONLNd{Y<_A(}Z
n
°dONLNd}UJa
@)2You can now set the values of the SR/CCR register.

°dONLNd∞o<uA(ìZ
n
°dONLNd≤kJw
ƒ)LSADE no longer uses the MPW Shell’s small icon for the Notification Manager.

°dONLNdˇÖ<ãA(©Z
n
°dONLNd

ÅJç
V)1SADE now works properly under VM on 040 machines.

°dONLNd
3õ<°A(øZ
n
°dONLNd
5óJ£_)The ,
Courier

°dONLNd
9ó_£É)Extras
°dONLNd
?óÉ£∫)$ menu item 

°dONLNd
Jó∫£)7    Show Self
°dONLNd
Só£
î)6# has been separated into two items:

°dONLNd
x•`±ñ(Õ~Show **this
°dONLNd
Ñ•ñ±Ò)6(Command-4), and

°dONLNd
ñ¥`¿ë(‹~Show *this.°dONLNd
£…J’å(ÒhShow **this
°dONLNd
Æ…å’Ô)B functions exactly as 

°dONLNd
ƒ…Ô’
%)c    Show Self
°dONLNd
Õ…
%’
⁄)6$ did in SADE 1.3 Final. However, for°dONLNd
Ú◊J„
=(ˇh.C++ programmers who are not using MacApp, the 

°dONLNd ◊
=„
y)Û
Show *this
°dONLNd*◊
y„
”)< menu item is more°dONLNd=ÂJÒ
(

h)useful. Therefore, we have included both.

°dONLNdh
+<
;˙(
VZChanges Since SADE 1.3B2
 
@X
@

°dONLNdÅ
S<
YA*!
n
°dONLNdÉ
OJ
[
‹)TCFront  generates incorrect symbols for any PascalObject with a forward declaration.°dONLNdÿ
]J
i
*+In the member functions, CFront  says that 

°dONLNd
]

i
0)Œthis
°dONLNd
]
0
i
F) is a 

°dONLNd

]
F
i
j)*TType
°dONLNd
]
j
i
‡)$, then casts all references°dONLNd/
kJ
wr(
ìhthrough 

°dONLNd7
kr
wä)(this
°dONLNd;
kä
wô) to 

°dONLNd?
kô
wˇ)(**(TType**)this)
°dONLNdP
kˇ
w
‡)f/. To alleviate this problem some hacks were put°dONLNdÄ
yJ
Ö
3(
°h0in SADE.  If your program contains the resource 

°dONLNd∞
y
3
Ö
{)È%__MethTable
°dONLNdº
y
{
Ö
◊)H (as is the case with°dONLNd“
áJ
ì
Ã(
ØhPMacApp programs), and if you have a type which the symbol file specifies to be a°dONLNd#
ïJ
°
`*=pointer to a PascalObject (a record whose first element is a 

°dONLNd`
ï
`
°
ê(
Ω
~__vtable
°dONLNdh
ï
ê
°
Œ)0), SADE will°dONLNdu
£J
Ø
ÿ(
Àh[make itself believe that the type really is a pointer to a pointer to that object. As a con°dONLNd–
£
ÿ
Ø
‹(
À
ˆ
-°dONLNd—
±J
Ω
ÿ(
ŸhWsequence of this fix, if you singly dereference a handle to a PascalObject, the pointer°dONLNd)
øJ
À
ò*Ivalue displayed will be correct, but the type displayed will be a handle.°dONLNdt
€J
Á„*The newly provided menu item  

°dONLNdí
€„
Á
”)ô(Twice Dereference Selection (Command-5),
°dONLNdª
ÈJ
ı
¢(hFexplained below, makes displaying objects through handles much easier.

°dONLNd<    A('Z
n
°dONLNd
ˇJß)A new menu called 

°dONLNd
ˇßÀ)]Extras
°dONLNd
ˇÀ
‡)$7 was added. Four of the menu items under this menu make°dONLNdT
J
‹(5hWdisplaying objects easier, and the last one makes changing the value of objects easier.°dONLNd≠#J/Q*• 

°dONLNdØ#Q/
)!Show Value In Context (Command-2)
°dONLNd–#
/
+)Δ and°dONLNd÷9JEQ(ah• 

°dONLNdÿ9QE
e).Show Dereferenced Value In Context (Command-3)°dONLNdO<[B(wZ
 
°dONLNd
OJ[
“)OThe old style Show Value menu items have no context, they simply follow scoping°dONLNdZ]Ji√*rules. Thus, if you select 

°dONLNdu]√i·)yfNext
°dONLNdz]·i
í)', it will try to show you an automatic 

°dONLNd°]
íi
∞)±fNext
°dONLNd¶]
∞i
‹)
, a global

°dONLNd±kJwn(ìhfNext,
°dONLNd∑knwq)$
 

°dONLNd∏kqwπ)this^.fNext 
°dONLNdƒkπw√)Hor

°dONLNdΔk√w
)

 this^^.fNext
°dONLNd”k
w
)N
.°dONLNd÷ÅJç
Â(©hVThese new menu items put the value of the selected variable in a separate window.  For°dONLNd-èJõ
Ê*Wsubsequent selections, the name of the window provides the context.  E.g. if you select(·Z
SADE 1.3.3)“
2)aE.T.O. #14 Release Notesˇä◊#ˇˇˇˇˇ#◊

_,
Courier

.°dONLNd)J5h+hQfNext,Times
°dONLNd)h5Ô) in your source file and do a 

°dONLNd#)Ô5
%)á    Command-2
°dONLNd,)
%5
õ)6, you will most likely get

°dONLNdG7JCí(_hthis^^.fNext
°dONLNdS7íC
ó)H7.  However, if you had previously displayed a variable 

°dONLNdä7
óC
Õ(_
µ    newWindow
°dONLNdì7
ÕC
Â)6, and°dONLNdôEJQg(mhselect 

°dONLNd†EgQÖ)fNext
°dONLNd•EÖQ
[)) in that window, Command-2 will show you 

°dONLNdŒE
[Q
µ)÷newWindow.fNext
°dONLNd›E
µQ
π)Z
.°dONLNd‡aJm
“(âhTSince these windows are really files, when the length of the name of the thing to be°dONLNd
5oJ{
Õ*Rdisplayed exceeds 32 characters, it will be displayed in the Value window instead.°dONLNd
à}Jâ
Ÿ*SThese menus do not work if your selection has a colon (:) in it. These commands are°dONLNd
‹ãJó–*slightly slower than the regu°dONLNd
˙ã–ó
‚)Ü7lar show value menu items, but having a separate window°dONLNd2ôJ•
Q(¡h9for each variable far outweighs the slight speed penalty.°dONLNdmµJ¡Q*• 

°dONLNdoµQ¡œ)Set Value (Command-=)
°dONLNdÖ√Jœ
–(ÎhOChanging variables has always been difficult in SADE . The problem is that SADE°dONLNd’—J›
ÿ*Tshows you structured values, but you probably need to change only a field in a struc°dONLNd)—
ÿ›
‹(˘
ˆ
-°dONLNd*flJÎ
⁄(
hVtured object. It would be nice to type over a displayed value in a window to the value°dONLNdÅÌJ˘
&*0you want.  Unfortunately, it is not that simple.°dONLNd≥
J

Ÿ*WIf you are trying to change a simple variable, simply highlight its name and select the°dONLNd
J
~*
menu item 

°dONLNd
~
¥)4    Set Value
°dONLNd
¥

Ÿ)6=.  From the displayed dialog box, you can verify that SADE is°dONLNd\
J
+
‘(
GhVgoing to change the variable you wanted. If the proper object is selected, type in the°dONLNd≥
-J
9
Á*Uvalue you want.  You can type in expressions instead of simple numbers.  You can also°dONLNd    
;J
G
–*Stype in the name of a complex object whose type matches that of the left hand side.°dONLNd^
WJ
c
fl*WIn implementing this operation, SADE first evaluates the left hand side, then evaluates°dONLNd∂
eJ
q
fl*Uthe expression you typed in, and may display error messages if it finds any problems.°dONLNd

sJ

€*VAfter that SADE will try the actual assignment; that too may fail because of incompati°dONLNdc
s
€

fl(
õ
˘
-°dONLNdd
ÅJ
ç
(
©h,ble types for the left and right hand sides.°dONLNdí
ùJ
©
’*WTo change a field buried in a structure, you have to peel the outer levels. E.g. if you°dONLNdÍ
´J
∑ë*want to change

°dONLNd˙
∫`
Δ
+FirstLevel.SecondLevel->Member
°dONLNd
«J
”a(
Ôhdo a 

°dONLNd
«a
”ó)    Command-2
°dONLNd'
«ó
”
Ø)6: after selecting FirstLevel. This gives you a window named

°dONLNdb
’J
·Ü(
˝h
FirstLevel
°dONLNdl
’Ü
·
&)<". In that window, select the word 

°dONLNdé
’
&
·
h)†SecondLevel
°dONLNdô
’
h
·
ñ)B
 and do a 

°dONLNd£
’
ñ
·
Ã).    Command-3
°dONLNd¨
’
Ã
·
–)6
.°dONLNdÆ
„J
ÔÁ(hNow you have a window named 

°dONLNd 
„Á
Ô
q)ùFirstLevel.SecondLevel^
°dONLNd·
„
q
Ô
›)ä. In this window select°dONLNd˘
ÒJ
˝o(h    the text 

°dONLNd
Òo
˝ì)%Member
°dONLNd
Òì
˝
)$ and select Set Value or 

°dONLNd!
Ò

˝
:)q    Command-=
°dONLNd*
Ò
:
˝
>)6
.°dONLNd-J
#(/h(Two new menu commands were added to the 

°dONLNdU
#
G)ŸExtras
°dONLNd[
G
ƒ)$  menu to make debugging°dONLNdtJ!
(=h*MacApp applications written in C++ easier.°dONLNd†+J7ö*• The menu item 

°dONLNd∞+ö7
)PShow Self (Command-4) 
°dONLNdΔ+
7
H)Ñ    displays 

°dONLNdœ+
H7
l)***this
°dONLNd’+
l7
◊)$ in a separate window.°dONLNdÏ9JE
î(ahAYou must be stopped inside a MacApp method for this menu to work.°dONLNd    /UJa
Ã*JC++ programmers who are not using MacApp may wish to edit the SADE routine

°dONLNd    zcJoí*__ShowSelf__
°dONLNd    Ücío
è)H9 in the file SadeStartup file so that this menu displays 

°dONLNd    øc
èo
≥)˝*this 
°dONLNd    ≈c
≥o
ÿ)$instead.°dONLNd    œyJÖö(°h• The menu item 

°dONLNd    flyöÖ
ä)P(Twice Dereference Selection (Command-5) 
°dONLNd
y
äÖ
‹)makes displaying°dONLNd
áJì
ÿ(ØhUobjects through a handle to them a one step process. The value is displayed in a sepa°dONLNd
má
ÿì
‹(Ø
ˆ
-(·Z
SADE 1.3.3)“
3)aE.T.O. #14 Release NotesˇV◊#ˇˇˇˇˇ#◊

_,Times
.°dONLNd)J5
+hQ)rate window, as in the previous commands.°dONLNd+EJQ
Á*VThis menu is implemented in the file SadeUserStartup•Extras.  You can remove this file°dONLNdÇSJ_
F*3without affecting SADE's behavior in any other way.,

Zapf Dingbats

°dONLNd∂m<sA(ëZ
n
°dONLNd∏iJu
J)6The order in which SADE startup files are executed is:°dONLNdJãN*
•

°dONLNdÒÉNâP)
 
°dONLNdÚPãâ)SadeStartup°dONLNdˇïJ°N(Ωh
•

°dONLNd
ôNüP)
 
°dONLNd

ïP°†)SadeUserStartup°dONLNd
´J∑N(”h
•

°dONLNd
ØNµP)
 
°dONLNd
´P∑
fl)Uall files whose names starts with SadeUserStartup•. These files are executed in alpha°dONLNd
i´
fl∑
„(”
˝
-°dONLNd
jπJ≈à(·hbetical order.°dONLNd
z›JÈ
◊*$UIf you want to override anything defined in the file SadeUserStartup•Extras, create a°dONLNd
–ÎJ˜
¡*Rfile named something like SadeUserStartup•zzz, so that it is alphabetically later.

°dONLNd#
<
A(
)Z
n
°dONLNd%

J


b)=SADE will place all temporary files in the sub-folder called ,
Courier

°dONLNdb


b


™(
)
ÄSADE Scratch
°dONLNdn


™


⁄)H inside the°dONLNdz
J

·(
7hXSADE launch directory.  If the folder does not exist, SADE will create it.  During exit,°dONLNd”
J
)
d*<SADE will delete all SADE created files from this directory.°dONLNd
9J
E
€*UOne side effect of this behavior is that SADE will no longer remember the position of°dONLNdg
GJ
S
Ê*Wthe temporary windows like Values. If you prefer the old behavior, override the scratch°dONLNdø
UJ
a
$*/directory by adding the following line to your 

°dONLNdÓ
U
$
a
~)⁄SadeUserStartup
°dONLNd˝
U
~
a
ì)Z file:

°dONLNd
d`
pˆ(
å~__ScratchDir__ := SADEDir

°dONLNd
}<
ÉA(
°Z
n
°dONLNd!
yJ
Ö
’)QWhen SADE needs to open a source file, it tries much harder now.  The symbol file°dONLNds
áJ
ì
—*Rprovides SADE with either a full path name or just the leaf name, depending on the°dONLNdΔ
ïJ
°
‡*Xway the file was compiled. In addition, the modification date of the source file when it°dONLNd
£J
Ø
÷*Twas last compiled is also provided. Here is the list of actions SADE goes through to°dONLNdt
±J
Ωú*find a source file:°dONLNdâ
«J
”
Œ*S• Check if any of the open files have the same leaf name and matching date. If not,°dONLNdfi
›J
È
·*]• If the symbol table specified a full path name, try the full path to open the file. If not,°dONLNd=
ÛJ
ˇ
§*N• Try to find a file in the default directory with the same leaf name. If not,°dONLNdç    J
ã*I• Try to find a file in any of the directories in the SourcePath. If not,°dONLNdÿJ+
»*R• Check if any of the open files have the same leaf name but a wrong date. If not,°dONLNd,5JA
‡*Z• Ask the user to navigate the directory structure to find a file with the same leaf name.°dONLNdàKJW
–*UCheck the modification date of the file found in any of the above ways, if there is a°dONLNdfiYJe
‚*Zmismatch, give the user a chance to find a better match. If the user finds a file in a new°dONLNd9gJs
;*4directory, add the new directory to the source path.

°dONLNdnÅ<áA(•Z
n
°dONLNdp}Jâ
›)YIf you open a source file in a directory which is not in the current source path, and try°dONLNd ãJó
Ê*Yto set a break point in it, if SADE finds the symbol for a file with that name, SADE will(·Z
SADE 1.3.3)“
4)aE.T.O. #14 Release Notesˇ
Æ◊#ˇˇˇˇˇ#◊

_,Times
.°dONLNd)J5

+hQ)add the new directory to the source path.,

Zapf Dingbats

°dONLNd*C<IA(gZ
n
°dONLNd,?JK
‘)SWhen SADE displays a record, the name of the record is displayed in addition to its°dONLNdÄMJY
L*4contents.  Occasionally SADE may display names like ,
Courier

°dONLNd¥M
LY
j(u
j__O32
°dONLNdπM
jY
Ÿ), these are generated by°dONLNd“[Jgë(ÉhCFront in situa°dONLNd‚[ëg
L)G'tions like anonymous unions or structs.

°dONLNd

u<{A(ôZ
n
°dONLNd
qJ}
⁄)XWhen the conditional break table is full, we shift the oldest break point out instead of°dONLNd
eJã
*Ddeleting all old conditional breakpoints. You still get the warning.

°dONLNd
™≈<’˙(ZChanges Since SADE 1.3B1
 ⁄X⁄

°dONLNd
√Ì<ÛA*!
n
°dONLNd
≈ÈJı
‹)SSADE will now set the Sourcepath variable for you.  If SADE cannot find the applica°dONLNdÈ
‹ı
‡(

˙
-°dONLNd˜J

◊(
hXtion’s source files in the same directory as the symbol file, it will prompt you to find°dONLNdr
J

Ÿ*Vthe source file.  In addition, while debugging your code, if you step into a procedure°dONLNd…
J

–*Ydefined in a separate source file and that file is in a different directory than those de°dONLNd"

–

‘(
;
Ó
-°dONLNd#
!J
-Õ(
Ihfined by the sourcepath vari°dONLNd@
!Õ
-
‡)É;able, SADE will prompt you to search for that file as well.°dONLNd|
/J
;
j(
Wh<SADE will add the new directory indicated to the sourcepath.°dONLNd∫
EJ
Q
’*RNote, however, that SADE does not clear the Sourcepath variable each time you kill°dONLNd

SJ
_
’*Syour application. This way, you can continue targeting the same application without°dONLNda
aJ
m
`*9SADE prompting you each time to locate your source files.

°dONLNdõ
{<
ÅA(
üZ
n
°dONLNdù
wJ
É
‰)TSC7 is a new script available in the SADE folder.  When executed from the worksheet,°dONLNdÚ
ÖJ
ëÃ*you may use the procedure 

°dONLNd
ÖÃ
ë
)ÇStackCrawl7
°dONLNd
Ö

ë
)B or 

°dONLNd
Ö

ë
6)sc7 
°dONLNd
Ö
6
ë
ÿ)#defined in the script to show a pos°dONLNdB
Ö
ÿ
ë
‹)¢
-°dONLNdC
ìJ
ü
„(
ªhUsible calling chain sequence.  StackCrawl7 is similar to the MacsBug command sc7.  It°dONLNdô
°J
≠î*is useful for dis°dONLNd´
°î
≠
Â)JEplaying the calling sequence when the built in A6 based stack command°dONLNdÒ
ØJ
ªí(
◊hdoes not work.

°dONLNd
…<
œA(
ÌZ
n
°dONLNd
≈J
—
Ê)PMacsBug and ROM symbols will now be displayed in a disassembly. When there is no°dONLNdS
”J
fl^*sym°dONLNdW
”^
fl
⁄)Lbolic information available and your code has been compiled with MacsBug sym°dONLNd£
”
⁄
fl
fi(
˚
¯
-°dONLNd§
·J
Ì
D(    h2bols, SADE will display MacsBug information, e.g.:°dONLNdŸ
˜`
E+)BEQ.S      µINITIALIZE+$00BA   ; 00BE7B22

°dONLNd<A(5Z
n
°dONLNd
J
Ÿ)WSADE will now display up to the first 20 elements of an array instead of just the first°dONLNd]J'r*element.(·Z
SADE 1.3.3)“
5)aE.T.O. #14 Release Notesˇæ◊#ˇˇˇˇˇ#◊

_,

Zapf Dingbats

.°dONLNd-<3A+ZQ
n,Times
°dONLNd)J5
Δ)PWhen displaying the value of a pointer to a string, SADE will always display the°dONLNdS7JC
ä*Hpointer value, then the string if it meets the criteria described below.

°dONLNdúQ<WA(uZ
n
°dONLNdûMJY
Ê)XC does not have a built-in string type. The following heuristic is employed to determine°dONLNd˜[Jg
Q*:if a signed or unsigned character array contains a string:,
Courier

°dONLNd
3j`v
8+$// Get past the printable characters°dONLNd
Yx`ш*for (i = 1; i < len; i++)°dONLNd
uÜÑí
û+$/if (!isgraph(string[i]) && !isspace(string[i]))°dONLNd
®î®†Ã+$break;°dONLNd
≥∞`º
z(ÿ~/// Is this a CStr?  Must terminate with a null.°dONLNd
‰æ` “*if (string[i] == 0)°dONLNd
˙ÃÑÿ
V+$#// The first byte must be printable°dONLNd ⁄ÑÊ
í*-if (isgraph(string[0]) || isspace(string[0]))°dONLNdQË®Ù
+$goto display_CStr;°dONLNdh
`

Œ(
,~=// Is this a PStr?  The string[length] byte must be printable°dONLNdß
`
Ã*if (string[0] < i)°dONLNdº
 Ñ
,+$goto display_PStr;
°dONLNd–
5J
A
fi(
]h[The significance of this is that if you have partially constructed strings in a char array,°dONLNd,
CJ
O
’*QSADE may decide you do not have a string. If string display fails, SADE will show°dONLNd~
QJ
]
·*Vyou the first 20 elements of your array, which may give you a clue as to why the array°dONLNd’
_J
k
÷*Wdid not display as a string.  One peculiar case is when the first element of your array°dONLNd-
mJ
y
ÿ*Vcontains a zero, in which case SADE will believe that it successfully displayed a null°dONLNdÑ
{J
á
€*Ystring, and will not show the rest of the array.  In most cases this is the right answer,°dONLNdfi
âJ
ïì*but not always.°dONLNdÔ
üJ
´
ò*IAlso note that you can type coerce your array to display it as a PString:

°dONLNd;
∂`
¬ÿ+^PString(@YourArray)
°dONLNdQ
ÀJ
◊
s(
ÛhASimilarly,  you can coerce your array to display it as a CString:

°dONLNdï
‚`
Óÿ+^CString(@YourArray)
°dONLNd´
˜J
c(h<Note that Pascal strings are shown with single quotes, e.g. 

°dONLNdÁ
˜
c
ì(
Å'string'
°dONLNdÔ
˜
ì
Â)0, whereas C style°dONLNd
J¯(-h%null-terminated strings are shown as 

°dONLNd&¯
()Æ"string"
°dONLNd.
(
,)0
.

°dONLNd0K<[í(vZXCMDs, etc.
 `X`

°dONLNd<s<yA*!
n
°dONLNd>oJ{
‡)TSADE’s default behavior does not allow you to set breakpoints in resources which are°dONLNdì}Jâ
’*Rnot of the type 'CODE'.  You can change this behavior by setting the built-in SADE°dONLNdÊãJór*    variable 

°dONLNdÔãrófi)(BreakInNonCODERsrc
°dONLNd
ãfió
‘)l1 to 1. Be warned, however, that as SADE must then(·Z
SADE 1.3.3)“
6)aE.T.O. #14 Release Notesˇp◊#ˇˇˇˇˇ#◊

_,Times
.°dONLNd)J5é+hQcheck every re°dONLNd)é5
fi)DFsource which is being loaded into memory, this option will slow things°dONLNdV7JCi(_hdown.,

Zapf Dingbats

°dONLNd\Q<WA(uZ
n
°dONLNd^MJY
Œ)FYou can debug HyperCard XCMDs and XFCNs with SADE. To be able to debug°dONLNd•[Jg“*XCMDs, follow these steps.°dONLNd¡iNu\+(1)°dONLNd≈iiu
Ñ)Compile and link your XCMD (or XFCN ) with symbolics.°dONLNd˚wNÉ\(ül(2)°dONLNdˇwiɵ)Using ResEdit, 
°dONLNd
wµÉfi)Lremove°dONLNd
wރ
·))6 the XCMD resource out of the original stack and paste°dONLNd
KÖië
!(≠á)it into the HyperCard application itself.°dONLNd
uìNü\(ªl(3)°dONLNd
yìiü
Ω)@In SADE, you must set the SADE variable BreakInNonCODERsrc to 1.°dONLNd
º°N≠\(…l(4)°dONLNd
¿°i≠
”)PSet the directory to the location of the .SYM file and set the sourcepath to the°dONLNdØiª|*loca°dONLNdØ|ªfl)tion of your sources.°dONLNd.ΩN…\(Âl(5)°dONLNd2Ωi…
R)Next, target HyperCard using the SYM file, e.g.:,
Courier

°dONLNdcÃ`ÿ
>(Ù~%Target "HD:HyperCard:Hypercard" using°dONLNdâ⁄`Ê
*"HD:Examples:HyperXExample.SYM"
°dONLNd™ıi


fi+    OYou will see an “Initial program break encountered at...” message output to the°dONLNd˙
i

€*Jworksheet, which indicates HyperCard itself was suspended.  From here, you°dONLNdE
i

∑*Emay open your source file, set a breakpoint and execute your program.°dONLNdå
'J
3
◊(
OhTNote: this is not a fully supported feature of SADE.  Therefore, the above steps may°dONLNd·
5J
A¡*not work in all instances.

°dONLNd¸
O<
UA(
sZ
n
°dONLNd˛
KJ
W
‰)QSome applications may load your XCMD-type code resources in a subheap. To be able°dONLNdP
YJ
e
v*?to debug them, you need to set another built-in SADE variable, 

°dONLNdè
Y
v
e
ƒ(
Å
î
CurTargetZone
°dONLNdú
Y
ƒ
e
Â)N, to the°dONLNd•
gJ
sU(
èhad°dONLNd®
gU
sΩ)dress of that subheap.

°dONLNdø
Å<
áA(
•Z
n
°dONLNd¡
}J
â
‡)ODebugging printer drivers is analogous to debugging XCMDs and XFCNs.  Build the°dONLNd
ãJ
ó
·*Tdriver and paste the code resource you wish to debug into any application.  Remember°dONLNdf
ôJ
•
‹*Xto place the driver in the extensions folder (System 7.0) and select the driver from the°dONLNdø
ßJ
≥
≈*PChooser.  Set the directory and sourcepath as mentioned above.  Set the variable

°dONLNd
µJ
¡∂*BreakInNonCODERsrc
°dONLNd"
µ∂
¡
‘)l? to 1.  Target the application using the .SYM file you just cre°dONLNda
µ
‘
¡
ÿ(
›
Ú
-°dONLNdb
√J
œ
’(
ÎhOated.  You may now set a break in your source file and execute the SADE command

°dONLNd≤
—J
›V*Go
°dONLNd¥
—V
›Z)
.

°dONLNd∂<'í(BZ
Known bugs
 ,X,

°dONLNd¡?<EA*!
n
°dONLNd√;JG
Œ)NIf you target an MPW tool and then before executing the tool from the MPW work°dONLNd;
ŒG
“(c
Ï
-°dONLNdIJU
‰(qhWsheet, you set a break on the tool and quit SADE, the Shell may crash with a bus error.

°dONLNdkc<iA(áZ
n
°dONLNdm_Jk
÷)TIf you step over the last statement in an MPW tool written in Pascal, you may get an°dONLNd¬mJyƒ*address error in the Shell.

°dONLNdfiá<çA(´Z
n
°dONLNd‡ÉJè
”)QThe SADEKey may not work until the target application has made an event call (for(·Z
SADE 1.3.3)“
7)aE.T.O. #14 Release Notesˇh◊#ˇˇˇˇˇ#◊

_,Times
.°dONLNd)J5«+hQinstance, WaitNextEvent).°dONLNd?JK
Ñ*?Pressing the SADEKey multiple times in a row may cause a crash.°dONLNd\UJa
∏*JTargeting a running application and then hitting the SADEKey may not work.,

Zapf Dingbats

°dONLNdßo<uA(ìZ
n
°dONLNd©kJw_)The ,
Courier

°dONLNd≠k_wÉ)Stack 
°dONLNd≥kÉw
t)$/command does not support the documented option 

°dONLNd‚k
tw
Ü)Òat 
°dONLNdÂk
Üw
Æ)address.

°dONLNdÓÖ<ãA(©Z
n
°dONLNdÅJçf)If the 

°dONLNd˜Åfçä)Stack 
°dONLNd˝Åäç
÷)$Hcommand is part of a break action, the stack will not necessarily be dis°dONLNd
EÅ
֍
⁄(©
Ù
-°dONLNd
FèJõ
—(∑hPplayed when the breakpoint is encountered.  A Printf command following the stack°dONLNd
óùJ©
~*@command will flush internal buffers, forcing any pending output.

°dONLNd
ÿ∑<ΩA(€Z
n
°dONLNd
⁄≥Jø
ÿ)SSADE shows Pascal variables containing sets as integers, instead of showing the set°dONLNd.¡JÕ»*elements with their names.

°dONLNdI€<·A(ˇZ
n
°dONLNdK◊J„
Ê)VIf you kill the target using the menu command, the watch variables are removed and the°dONLNd¢ÂJÒ
≤*Iconditional break table is cleared. However, if you use the SADE command °dONLNdΉ
≤
Œ(


–Kill°dONLNdÔÂ
ŒÒ
fl), or°dONLNdÙÛJˇ
◊(
hXquit the target, these clean up actions are not done. If you target again, the old watch°dONLNdM

J

◊*variables may not be relevant.

°dONLNdl
<
!A(
?Z
n
°dONLNdn
J
#
‡)VThere is a size limit of 1,006 bytes on the value which can be assigned to a SADE vari°dONLNdƒ

‡
#
‰(
?
˛
-°dONLNd≈
%J
1
—(
MhQable.  As a consequence of this, you can not use the Show Value menu to display a°dONLNd
3J
?
–*Svariable of size greater than 1,006 bytes.  You can, however, enter the name of the°dONLNdk
AJ
M
æ*Qvariable you want to display in a writable window and hit enter to get its value.

°dONLNdΩ
[<
aA(
Z
n
°dONLNdø
WJ
c
G)6Assigning a large C structure to a SADE variable in a 

°dONLNdı
W
G
c
k)˝define
°dONLNd˚
W
k
c
÷)$ statement may display°dONLNd
eJ
q¯(
çh%garbage as part of the error message.

°dONLNd8
<
ÖA(
£Z
n
°dONLNd:
{J
á
‚)UTo reference Pascal variables declared at UNIT scope, when the PC is not in the scope°dONLNdê
âJ
ïÀ*of the unit, use the syntax, 

°dONLNd≠
âÀ
ï—)Å
\
°dONLNdÆ
â—
ï
)UNITNAME

°dONLNd∂
â

ï
)?
.
°dONLNd∑
â

ï
T)variablename°dONLNd√
â
T
ï
‰)>. To reference Pascal variables°dONLNd„
óJ
£
$(
øh*declared at PROGRAM scope use the syntax, 

°dONLNd

ó
$
£
*)⁄
\
°dONLNd
ó
*
£
k)variableName°dONLNd
ó
k
£
Õ)A; referencing them as

°dONLNd0
•J
±P(
Õh
\
°dONLNd1
•P
±¨)PROGRAMNAME

°dONLNd<
•¨
±≤)\
.
°dONLNd=
•≤
±Û)variableName°dONLNdI
•Û
±
>)A does not work.

°dONLNdY
ø<
≈A(
„Z
n
°dONLNd[
ªJ
«
Ê)QWhen running SADE on a Classic and targeting a MacApp program, once you step into°dONLNd≠
…J
’
æ*Ka MacApp method, SADE can’t retrieve the symbol information for the source.

°dONLNd˘
„<
ÈA(Z
n
°dONLNd˚
flJ
Î
Ê)XIf Stop Before Constructor is set and after targeting you step over main() in a C or C++°dONLNdT
ÌJ
˘
Á*[application, quitting the application will produce an error message of "Data Initialization°dONLNd∞
˚Jt*    Failed!".

°dONLNdª<A(9Z
n
°dONLNdΩJ
‚)SStepping over a CHK or TRAPV instruction which will cause an exception results in a°dONLNdJ+g*crash.

°dONLNd9<?A(]Z
n
°dONLNd5JA
‹)VIf you enter SADE by calling a SysError() call, the condition code registers displayed°dONLNdqCJOë*will be invalid.

°dONLNdÇ]<cA(ÅZ
n
°dONLNdÑYJe
÷)OSince SADE allows users to use symbol files which may not have been produced as°dONLNd‘gJs
—*Spart of the application build, SADE can not do any checking of the symbol file date°dONLNd    (uJÅ
d*?relative to the application date. If you see the error message:

°dONLNd    iÑ`ê
‡+@Logical end-of-file reached during read operation (OS error -39)
(·Z
SADE 1.3.3)“
8)aE.T.O. #14 Release Notesˇÿ◊#ˇˇˇˇˇ#◊

_,Times
.°dONLNd)J5
‡+hQVwhen you target a process, it probably means that your application and the symbol file°dONLNdW7JCî*are out of sync.,

Zapf Dingbats

°dONLNdhQ<WA(uZ
n
°dONLNdjMJY
Õ)RThe current symbolic information does not include information specific to classes.°dONLNdΩ[Jg
*"While SADE supports commands like ,
Courier

°dONLNdfl[
g
H)∂Break Class °dONLNdÎ[
Hg
Ñ)H
TSomething
°dONLNdı[
Ñg
Á)<, it requires SADE to°dONLNd
iJu
‰(ëhWscan the entire symbol file to find matching names.  As a result, this command can take°dONLNd
cwJÉÇ*a long time.

°dONLNd
që<óA(µZ
n
°dONLNd
sçJô
Œ)SSimilarly, the symbolic information does not include information about static class°dONLNd
«õJß
fl*Uvariables, and SADE does not display these when a class object is displayed. To see a°dONLNd©Jµë*class static vari°dONLNd/©ëµ
f)G.able, you have to fully qualify the name, e.g.

°dONLNd_∏`ƒÿ(‡~TClass:fgStaticField

°dONLNdt—<◊A(ıZ
n
°dONLNdvÕJŸ
›)WIf you have trace points set within the main event loop of your target program, so that°dONLNdŒ€JÁ
⁄*Uthey are continually displayed in the worksheet, the target application's menu may oc°dONLNd#€
⁄Á
fi(

¯
-°dONLNd$ÈJı
”(
hQcasionally overlap the SADE menu.  This is only a cosmetic problem in the Process°dONLNdv˜J

‹*SManager (System 7.0) and in Multifinder (System 6.0) and should not affect the func°dONLNd…˜
‹

‡(

˙
-°dONLNd 
J
≈(
-htionality of your program.

°dONLNdÂ
<
%A(
CZ
n
°dONLNdÁ
J
'
‹)RUsers of Object Pascal who are not using MacApp should always specify the linker's°dONLNd:
)J
5Á*!method table optimization option 

°dONLNd[
)Á
5
)ù-opt on
°dONLNdb
)

5
‚)*,. Otherwise, stepping over method calls will°dONLNdè
7J
C
’(
_hRnot work.  This is because SADE changes the return address of the method’s caller,°dONLNd‚
EJ
Q
Á*Qwhich confuses the method dispatch procedure (%_Method).  When %_Method fails, it°dONLNd4
SJ
_
ò*Fintentionally executes a division by zero, which is what SADE reports.

°dONLNd{
m<
sA(
ëZ
n
°dONLNd}
iJ
u
ÿ)QSADE  cannot target background-only applications because of the way it works with°dONLNdœ
wJ
É
‰*Rthe  Process Manager.  Workaround: Remove the background-only restriction from the°dONLNd"
ÖJ
ëk*applica°dONLNd*
Ök
ë
€)!Ltion and debug.  Once your application is fully debugged, make it background°dONLNdv
Ö
€
ë
fl(
≠
˘
-°dONLNdw
ìJ
ü(
ªhonly again.


°dONLNdÉ
«<
‘¡(
ZSystem 7.0 specific bugs 
‚X
‚

°dONLNdú
Í<
A*
n
°dONLNdû
ÊJ
Ú
ÿ)TUnder System 7.0, if you’ve targeted an application and stepped through your initial°dONLNdÚ
Ê
ÿ
Ú
‹(
ˆ
-°dONLNdÛ
ÙJ
fl(hUization code, even though your target is suspended, hiding SADE will cause the target°dONLNdIJ
"*.to run.  This is a bug in the Process Manager.

°dONLNdx<"A(@Z
n
°dONLNdzJ$
ƒ)RIf a file is open modifiable from a shared volume by one user, that file cannot be°dONLNdÕ&J2
1*1opened (read-only) for targeting by another user.

°dONLNd@<FA(dZ
n
°dONLNd<JH
Ÿ)SDo not launch two debuggers at the same time.  If you quit the second one launched,°dONLNdVJJV
ñ*Iand try any operation in the first one, you will get the cryptic message:

°dONLNd†YJe
‚*D#   Application made module calls in improper order  (OS error -603)
(·Z
SADE 1.3.3)“
9)aE.T.O. #14 Release Notesˇ$◊#ˇˇˇˇˇ#◊

_,Times


.°dONLNd)<6¡+ZRSystem 6.0 specific bugs DXD,

Zapf Dingbats

°dONLNdM<SA*
n
°dONLNdIJU
Ê)QSpecial care needs to be taken when debugging MacApp programs under system 6.0.x.°dONLNdnWJc
Á*[After killing a program the first time, you may not be able to retarget the application and°dONLNd eJq
Ã*Qbe forced to reboot.  This is because MacApp installs a VBL which is not being re°dONLNd
e
Ãq
–(ç
Í
-°dONLNd
sJ
–(õhQmoved by MultiFinder after a kill.  This does not occur under system 7.0.  A work°dONLNd
nÅJç
Œ*Taround is to always quit your application normally; do not kill the application from°dONLNd
√èJõl*SADE.

°dONLNd
…©<ØA(ÕZ
n
°dONLNd
À•J±
‚)VSADE doesn’t handle script execution properly when the script is in the same folder as°dONLNd"≥Jø
ª*Rthe target.  Workaround: fully qualify the path to the script before executing it.

°dONLNduÕ<”A(ÒZ
n
°dONLNdw…J’
◊)TThere is a bug in Multifinder 6.1b9 which prevents you from being able to scroll the°dONLNdÃ◊J„
+*,Apple Menu when the option key is held down.

°dONLNd˘Ò<˜A(
Z
n
°dONLNd˚ÌJ˘
Á)VIf you use the target command when you already have a suspended target, the old target°dONLNdR˚J
´*will not be restarted.

°dONLNdi
<
A(
9Z
n
°dONLNdk
J

fl)VIf you launch a target from SADE, and quit SADE without first killing it, when the tar°dONLNd¡

fl

„(
9
˝
-°dONLNd¬
J
+
‹(
GhWget quits, Multifinder will try to send a message to a non-existent process and cause a°dONLNd
-J
9ã*
system crash.

°dONLNd(
G<
MA(
kZ
n
°dONLNd*
CJ
O
F)/The SADEKey cannot be changed under System 6.0.

°dONLNdZ
]<
cA(
ÅZ
n
°dONLNd\
YJ
e
ª)GSADE does not work with Maxima™ or Virtual (both from Connectix Corp.).


°dONLNd§
ç<
ö
?(
∂Z+Compiler and Linker symbol generation bugs: 
®X
®

°dONLNd–
∞<
∂A*
n
°dONLNd“
¨J
∏
ÿ)SThe compilers do not generate type information unless considered necessary.  If you°dONLNd&
∫J
Δ
—*Thave a type declared but do not have any object of that type, possibly used only for°dONLNd{
»J
‘ï*casting, no sym°dONLNdã
ȕ
‘
Ê)KGbolics are generated for the type. Workaround: none. This is a compiler°dONLNd”
÷J
‚

(
˛h*feature to minimize the symbol table size.

°dONLNd˛
<
ˆA(Z
n
°dONLNd
ÏJ
¯
‡)VCFront typically generates constructor and destructor code at the beginning and end of°dONLNdW
˙J[*syn°dONLNd[
˙[
fi)Qtactic blocks, gives them separate symbolic information records, but maps them to°dONLNd≠J
€(0hVthe same location in the source file. One observed behavior is stepping multiple times°dONLNdJ"
fi*Von the same source statement. Also, in this situation if you do a Break followed by an°dONLNd[$J0û*Unbreak, the loca°dONLNdm$û0
‡)TDtion you set the breakpoint and the location you did the unbreak may°dONLNd≤2J>
¢(ZhInot be the same, even if the selection looks identical. Workaround: none.

°dONLNd¸L<RA(pZ
n
°dONLNd˛HJT
Â)WIf the source code contains a series of declarations with assignments, CFront  produces°dONLNdVVJbb*incor°dONLNd\Vbb
Œ)Mrect symbol information for these.  The observed behavior is that you need to°dONLNd™dJp
◊(åhTsingle step as many times as there are declarations, but SADE keeps highlighting the°dONLNdˇrJ~
‚*Yfirst statement in the series.  After sufficient number of steps, SADE will jump over all°dONLNd    YÄJå
/*/the declaration code at once. Workaround: none.(·Z
SADE 1.3.3)Ã10)gE.T.O. #14 Release Notesˇd◊#ˇˇˇˇˇ#◊

_,

Zapf Dingbats

.°dONLNd-<3A+ZQ
n,Times
°dONLNd)J5
Œ)OC++ allows variables to be declared anywhere within a block.  When a program is°dONLNdR7JC
fi*Ustopped in a block before a variable comes into scope, SADE will display an incorrect°dONLNd®EJQö*value for the vari°dONLNdªEöQ
Δ)PCable. A better behavior might be to say that the variable is not in°dONLNdˇSJ_i({hscope.

°dONLNd
m<sA(ëZ
n
°dONLNd
    iJu·) CFront  passes a temporary file ,
Courier

°dONLNd
)i·u
#)óC.pipe.code
°dONLNd
4i
#u
‚)B( to the C compiler. The C compiler incor°dONLNd
\i
‚u
Ê)ø
-°dONLNd
]wJÉ
5(üh7rectly assigns all global static variables to the unit 

°dONLNd
îw
5É
;)Î
C
°dONLNd
ïw
;É
Á)'. For this reason, references to static°dONLNd
ΩÖJë
€(≠hUvariables in a file other than the current one does not work as expected. Workaround:°dONLNdìJü~*instead of \

°dONLNdì~ü)4FileName.StaticName
°dONLNd2ìü
)r, try 

°dONLNd8ì
ü
U)
\C.StaticName
°dONLNdEì
Uü
Y)N
.

°dONLNdG≠<≥A(—Z
n
°dONLNdI©Jµ
÷)QSADE can not print the values of anonymous unions in C++ correctly.  If you have:

°dONLNdõµR¡¶+struct Outer {°dONLNd´¿`Ãú+
int field;°dONLNd∂ÀR◊X(Ûp
 °dONLNd∏À`◊fi)union {  // anonymous°dONLNd–÷Ñ‚ÿ+$int cant_find;°dONLNd··ÑÌ
*char another_cant_find;°dONLNd˙Ï`¯l(
~};°dONLNd˝˜R
¶(
p} Outer_thing;
°dONLNd

J

(
4h'SADE is unable to display the value of 

°dONLNd4



Å)πOuter_thing.cant_find
°dONLNdI

Å

’)~.  Workaround: If°dONLNd[
J
&
Ç(
BhCyou look at the struct that CFront makes, you will see a name like 

°dONLNdû

Ç
&
ö(
B
†__O1
°dONLNd¢

ö
&
‹) for the anony°dONLNd∞

‹
&
‡)B
-°dONLNd±
(J
4ø(
Phmous union.  If you say 

°dONLNd…
(ø
4
[)uOuter_thing.__O1.cant_find
°dONLNd„
(
[
4
Œ)ú then SADE will print it.

°dONLNd˛
B<
HA(
fZ
n
°dONLNd
>J
J
÷)QThe  MPW 3.2 C compiler produces incorrect source statement information for state°dONLNdQ
>
÷
J
⁄(
f
Ù
-°dONLNdR
LJ
X
÷(
thRments with zero effect. The symptom is SADE's inability to set breakpoints in some°dONLNd•
ZJ
f
–*Oroutines. These show up most commonly in the process of compiling the output of°dONLNdı
hJ
tÃ*CFront. Workaround: give 

°dONLNd
hÃ
t
)Ç    -opt off 
°dONLNd
h

t
a)6flag to the compiler.

°dONLNd-
Ç<
àA(
¶Z
n
°dONLNd/
~J
ä
◊)QBoth the MPW 3.2 C and Pascal compilers may assign multiple user variables to the°dONLNdÅ
åJ
ò
Ê*Ysame register. As a consequence, if you try to display a register variable whose value is°dONLNd€
öJ
¶
ô*Ccurrently dead, the value displayed may be wrong. Workaround: none.

°dONLNd
¥<
∫A(
ÿZ
n
°dONLNd!
∞J
º
‹)UIf an enclosed Pascal procedure does not use any variable from the calling procedure,°dONLNdw
æJ
 
Â*Xthe MPW 3.2 Pascal compiler optimizes away the static link, but does not reflect this in°dONLNd–
ÃJ
ÿ
Ÿ*Vthe symbol information, resulting in incorrect display of arguments in the called func°dONLNd&
Ã
Ÿ
ÿ
›(
Ù
˜
-°dONLNd'
⁄J
Ê∏(htion. Workaround: use 

°dONLNd=
⁄∏
ÊË)n-opt on,
°dONLNdE
⁄Ë
ÊÎ)0
 

°dONLNdF
⁄Î
Ê
)nostatic
°dONLNdN
⁄

Ê
<)0 or the 

°dONLNdV
⁄
<
Ê
r)!    -opt off 
°dONLNd_
⁄
r
Ê
«)6flags to the Pascal°dONLNds
ËJ
Ùw(h    compiler.

°dONLNd}<A(&Z
n
°dONLNd
˛J

;)/The MPW 3.2 Pascal compiler optimizes away the 

°dONLNdÆ
˛
;

S)ÒLINK
°dONLNd≤
˛
S

») instruction for functions°dONLNdÕJ
„(4hZwhich do not need stack storage for local variables, resulting in incorrect display of the°dONLNd(J&¬*stack. Workaround: give 

°dONLNd@¬&¯)x    -opt off 
°dONLNdI¯&
x)6flag to the Pascal compiler.

°dONLNdf4<:A(XZ
n
°dONLNdh0J<
⁄)QThe MPW 3.2 Pascal compiler generates incorrect symbol information about the loca°dONLNdπ0
⁄<
fi(X
¯
-°dONLNd∫>JJ
ª(fhOtion of local variables that are assigned to a FPU register . Workaround: none.

°dONLNd
X<^A(|Z
n
°dONLNd    TJ`
”)OThe MPW 3.2 Pascal compiler generates incorrect symbol information for enclosed°dONLNd    \bJn
]*7functions with a procedure parameter. Workaround: none.

°dONLNd    î|<ÇA(†Z
n
°dONLNd    ñxJÑ
)*If your program contains single-statement 

°dONLNd    ¿x
Ñ
$)»for
°dONLNd    √x
$Ñ
”)$ loops which should execute multiple°dONLNd    ËÜJí
’(ÆhStimes, SADE will appear to step through the loop only once.  This is due to the way(·Z
SADE 1.3.3)Ã11)gE.T.O. #14 Release Notesˇ“◊#ˇˇˇˇˇ#◊

_,Times
.°dONLNd)J5
µ+hQIthat both the MPW 3.2 C and Pascal compilers generate symbol information.°dONLNdJ7JCæ*Workaround: set a break°dONLNdb7æC
E)tpoint on the statement in the ,
Courier

°dONLNdÄ7
EC
W)áfor
°dONLNdÉ7
WC
Ω) loop and execute the 

°dONLNdô7
ΩC
…)fGo
°dONLNdúEJQ¡(mhcommand multiple times.,

Zapf Dingbats

°dONLNd¥_<eA(ÉZ
n
°dONLNd∂[Jg
fl)QThe MPW C and Pascal compilers occasionally generate incorrect symbol information°dONLNd
iJu
*+for statement boundaries. Workaround: give 

°dONLNd
3i
u
T)‘    -opt off 
°dONLNd
<i
Tu
≥)6flag to the compiler.

°dONLNd
RÉ<âA(ßZ
n
°dONLNd
TJã
›)VThe current symbolic structure is somewhat limited in the size of the program that can°dONLNd
´çJô
Â*Vbe compiled with symbolics. The following table lists the number of different symbolic°dONLNdõJßfl* items a symbol file can contain.°dONLNd#±NΩ
+$Indexes to source statements (CSNTE)°dONLNdH±
<Ω
g)Ó    4 G lines°dONLNdT«N”Ê(Ôl Number of different source files°dONLNdu«
<”
K)Ó2K°dONLNdz›NÈ◊(
lNumber of Functions (MTE)°dONLNdî›
<È
Q)Ó64K°dONLNdöÛNˇœ(
lNumber of blocks (CMTE)°dONLNd≤Û
<ˇ
Q)Ó64K°dONLNd∏
    N

 (
1l(Number of Variables and Constants (CVTE)°dONLNd·
    
<

Q)Ó64K°dONLNdÁ
N
+–(
GlNumber of Types (TINFO)°dONLNdˇ

<
+
Q)Ó64K°dONLNd
5N
AÃ(
]lNumber of Labels (CLTE)°dONLNd
5
<
A
Q)Ó64K

°dONLNd#
O<
UA(
sZ
n
°dONLNd%
KJ
W
’)REven if you stay within the above limits, the MPW 3.2 linker occasionally produces°dONLNdx
YJ
e
J*7incorrect type information in large symbol tables. The 

°dONLNdØ
Y
J
e
Ü(
Å
h
Show Value
°dONLNdπ
Y
Ü
e
⁄)< menu item(s) nor°dONLNd 
Y
⁄
e
fi)T
-°dONLNdÀ
gJ
s
N(
èh9mally traps all internal errors and displays the message 

°dONLNd
g
N
s
“(
è
lUndefined/Out of scope
°dONLNd
g
“
s
÷)Ñ
.°dONLNd
uJ
Å
‰(
ùhTHowever, if you type the name of the object in the worksheet and hit enter, SADE may°dONLNdq
ÉJ
è–*then print the error message:

°dONLNdè
íJ
û
–*ASymbol table error: Variable type table index could not be found.
°dONLNd”
≠J
π
⁄*SWorkaround:  The post 3.2 version of the linker shipped on the E.T.O. #5 disk fixes°dONLNd'
ªJ
«
fl*Wmost of these problems. If you still find this problem, and if your program uses a rich°dONLNd
…J
’
Á*Xhierarchy of classes, there is no workaround.  Even with a partially broken symbol file,°dONLNdÿ
◊J
„
Â*Xyou may be able to do most of the things you need to do. If your program is just big, if°dONLNd1
ÂJ
Ò
‘*Rthe size of your symbol table exceeds 1 megabyte, consider compiling parts of your°dONLNdÑ
ÛJ
ˇ
ø*Mapplication without symbols, and compile only the suspect parts with symbols.°dONLNd”J
*(You can use the SADE diagnostic command 

°dONLNd˚

_)”List Symbol
°dONLNd
_
‘)B to see the local variables°dONLNd"J)
‘(EhSand types that are defined in the current scope. This command will also show if any°dONLNdv+J7ù*symbolic informa°dONLNdá+ù7
É)S3tion associated with these objects is inconsistent.

°dONLNdªE<KA(iZ
n
°dONLNdΩAJM
‚)TTypes which have global scope sometimes get  bound to a local scope, you can see the°dONLNdOJ[
 *Utype definition only if the type is used in the current scope, or a containing scope.°dONLNdh]Jiß*Workaround: none.(·Z
SADE 1.3.3)Ã12)gE.T.O. #14 Release Notesˇ:◊#ˇˇˇˇˇ#◊

_,Times

.°dONLNd)<9Í+ZTSADE 1.3 Manual Errata
 >X>,

Zapf Dingbats

°dONLNdS<YA*#
n
°dONLNdOJ[
œ)QThe manual’s index was not generated correctly, so you may notice that each entry°dONLNdk]Ji
”*V(after page 42) is off by two pages. Simply subtract the entry by 2 to get the correct°dONLNd¬kJwã*page number.

°dONLNdœÖ<ãA(©Z
n
°dONLNd—ÅJç
ƒ)OThe dialog box displayed when the target menu is selected is shown as a generic°dONLNd
!èJõ
∫*OSFGetFile dialog box. In the released product  the dialog box contains the line,
Courier

°dONLNd
rù`©
b++Please select an application or symbol file
°dONLNd
ùù
b©
f(≈
Ä
.

°dONLNd
†∑<ΩA(€Z
n
°dONLNd
¢≥Jø
fl)YIn the section describing the different ways to target a program,  the manual states that°dONLNd
¸¡JÕ
‹*Uyou can drag and drop the icon of the target application on top of the SADE icon. For°dONLNdRœJ€
}*@this feature to work, you may need to rebuild your desktop once.

°dONLNdïÈ<ÔA(

Z
n
°dONLNdóÂJÒ
‚)UThe Target menu command as described in the manual is incomplete.  It states that you°dONLNdÌÛJˇ
‡*Vmust select an application to debug, when in fact you may choose either an application°dONLNdD

J


fl*Yor its .SYM file from the dialog box.  Then, if both files are not in the same directory,°dONLNdû
J

€*USADE will prompt you to locate the missing file. For instance, if you select a symbol°dONLNdÙ
J
)v*file, e.g. °dONLNdˇ
v
)√),AppName.SYM°dONLNd

√
)
‚)M?.,  and the application file is not in the same directory, SADE°dONLNdJ
+J
7
,(
Sh3will put up a dialog asking you to locate the file °dONLNd}
+
,
7
\)‚AppName°dONLNdÑ
+
\
7
Ã)0.  (Your application and°dONLNdù
9J
E
R(
ah5.SYM file names do not have to be the same, however.)

°dONLNd”
S<
YA(
wZ
n
°dONLNd’
OJ
[
·)RThe manual states that if your target program is suspended and you quit SADE, SADE°dONLNd(
]J
i
Œ*Twill terminate the program. SADE will now restart your target application if it can.

°dONLNd}
w<
}A(
õZ
n
°dONLNd
sJ
¥)The description of the 

°dONLNdñ
s¥
)j
Show Stack
°dONLNd†
s

‰)<- menu command is incomplete.  The command now°dONLNdŒ
ÅJ
ç
ú(
©hGdisplays a warning if the program counter points to a LINK instruction.

°dONLNd
õ<
°A(
øZ
n
°dONLNd
óJ
£_)The 

°dONLNd
ó_
£É)Disasm
°dONLNd"
óÉ
£
¡)$? command correlates source statement numbers with assembly code°dONLNdb
•J
±
⁄(
ÕhSinstructions. Branch instructions which use the new branch island option, are shown°dONLNd∂
≥J
ø
*-with a ^ character to denote the indirection.

°dONLNd‰
Õ<
”A(
ÒZ
n
°dONLNdÊ
…J
’
⁄)TThe intentional bug introduced in the third C tutorial program, Sample2, can be more°dONLNd;
◊J
„
‹*Rdestructive than we intended. Running this program can cause your machine to hang.°dONLNdè
ÛJ
ˇ
›*UIf it does not hang your system, and you display the stack when the bus error occurs,°dONLNdÂ
J

Ê*Rthe output is more informative than documented, in that SADE displays some MacsBug°dONLNd8Jv*symbols.

°dONLNdA)</A(MZ
n
°dONLNdC%J1
‰)USADE acquired the ability to prompt for source files when needed after the manual was°dONLNdô3J?
–*Nfinalized.  As a consequence you may never have to use the SourcePath command.°dONLNdÈAJM
Á*VThis behavior is not documented in the SADE manual, but is described in some detail at°dONLNd    @OJ[ı*%the beginning of these release notes.(·Z
SADE 1.3.3)Ã13)gE.T.O. #14 Release Notesˇx◊#ˇˇˇˇˇ#◊

_,

Zapf Dingbats

.°dONLNd5<;A+ZY
n,Times
°dONLNd1J=
”)OSADE now includes an optional menu called Extras which is not documented in the°dONLNdR?JK
G*8manual, but is described earlier in these release notes.°dONLNdçUJa
‚*NContrary to what the SADE 1.3 Manual states, you can debug Hypercard XCMDs and°dONLNd‹cJo
‹*SXFCNs with SADE. The procedure for doing this is described earlier in these release°dONLNd
0qJ}g*notes.(·Z
SADE 1.3.3)Ã14)gE.T.O. #14 Release Notesˇ